System and method to identify customer premise equipment devices

ABSTRACT

A method and system for use in identifying customer premises equipment (CPE) in a distributed network are presented. The method utilizes a unique identifier provided by a CPE device to a host server during the discovery stage of PPPoE communications in a distributed network. The server receives the unique identifier and stores the identifier for use in identifying and managing CPE devices attached to a service provider&#39;s network. The host server is configured to receive an active discovery packet from a communications device. The active discovery packet has a tag comprising a device identifier field. The device identifier includes chipset and firmware information regarding remote DSL CPE.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This is a continuation application of U.S. patent application Ser. No.10/700,337, filed on Nov. 3, 2003, entitled “SYSTEM AND METHOD TOIDENTIFY CUSTOMER PREMISE EQUIPMENT DEVICES,” which is acontinuation-in-part application of U.S. patent application Ser. No.10/634,116, filed on Aug. 4, 2003 entitled “SYSTEM AND METHOD TOIDENTIFY DEVICES EMPLOYING POINT-TO-POINT OVER ETHERNET ENCAPSULATION,”the contents of which are expressly incorporated herein by reference intheir entirety.

BACKGROUND

1. Field of the Disclosure

The present disclosure relates to identifying characteristics pfcustomer premise equipment using point-to-point-over-Ethernet (PPPoE)service.

2. Description of the Related Art

Broadband service providers for distributed computing network servicessuch as digital subscriber line (DSL) service typically require the enduser, e.g., the home or business DSL subscriber, to employ a router,switch, or other customer premises equipment (CPE) to terminate the DSLconnection at the residence or business location. The router or otherCPE serves to terminate the Asynchronous Transfer Mode (ATM) connection,and generally utilizes point-to-point-over-Ethernet (PPPoE) enabledsoftware to complete the user authentication process.

When a DSL subscriber encounters a problem with their DSL connection,the DSL service provider has no way to automatically determine thespecific make and/or model of a particular CPE device being utilized bythe DSL subscriber. In this situation, telephone inquiries to thesubscriber are made to attempt to discover what type of equipment isbeing utilized at the CPE location, or a service technician isdispatched to “eyeball” the equipment when the customer does not knowwhat type of CPE device is at their location. Consider a typical case oftens of thousands (or even millions, in some cases) of DSL subscribersand their respective CPE devices, and the support problems presented tothe DSL service provider become evident.

In addition, when a service provider wishes to upgrade DSL transportservices in their service area(s), e.g., the provision of Point to PointProtocol Termination and Aggregation (PTA), it may be difficult tocost-effectively deploy the new service plan if the service providerdoes not know what types of CPE devices are currently deployed. Forexample, if a new transport service is scheduled for deployment in aspecific geographic region, but it is determined that a large number ofCPE devices may not support the new service, delays in deploymentresult. Such delays lead to increased provider costs, which aretypically passed along to the subscribers, resulting in higher rates.

Accordingly, there is a need for a system or method which is capable ofautomatically identifying CPE devices and their equipment type in aservice provider's service area.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a simplified diagram of a distributed network;

FIG. 2 is a simplified diagram of a customer premises equipment (CPE)device connected via an IP network to an access concentrator;

FIG. 3 is a flow diagram illustrating the stages of PPPoE discovery;

FIG. 4 is a block diagram of an ADSL bridge/router board whichincorporates a module configured to transmit a point-to-point overEthernet (PPPoE) active discovery packet, including a tag;

FIG. 5 illustrates a data packet for use in a distributed network;

FIG. 6 illustrates an Ethernet payload for point-to-point over Ethernet(PPPoE);

FIG. 7 illustrates a tag for use in an Ethernet payload;

FIG. 8 illustrates an example of a nine binary bit CPE device identifiercode embedded in the 0x0103 host-uniq tag;

FIG. 9 illustrates an embodiment of a host-uniq tag that includeschipset and firmware information;

FIG. 10 illustrates a system that utilizes the host-uniq taginformation;

FIG. 11 is a flow chart that illustrates a method of accessing DSL CPEinformation; and

FIG. 12 is a flow chart that illustrates use of the host-uniq tag ofFIG. 9

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DESCRIPTION OF THE DRAWINGS

The present disclosure provides a method, system, and apparatus for usein identifying customer premises equipment (CPE) in a distributednetwork. The method utilizes a unique device identifier that is providedby a CPE device during the discovery stage of point-to-point overEthernet (PPPoE) communications in a distributed network. A host servercollects this CPE-provided information, which may be used by a broadbandservice provider to identify, and thus manage, the CPE devices whichform a part of the service provider's network domain. An example of adistributed network system including a collection of domains with one ormore networks is illustrated in FIG. 1. An exemplary device identifierincludes chipset and firmware information regarding the DSL CPE and isillustrated in FIG. 9.

FIG. 1 is a simplified example of a distributed network, and is referredto as distributed network system 100. Distributed network system 100 caninclude numerous routing domains 103 and 105, which are connected to abackbone network 101. In a hierarchically arranged network system,backbone 101 is the central connection path shared by the nodes andnetworks connected to it. The backbone 101 administers the bulk oftraffic between communicating nodes to provide end-to-end servicebetween one user, for example, source node 121 in domain 103, andanother user, for example destination node 142.

Each routing domain 103, 105 in distributed network system 100 is acollection of one or more local networks that are attached to thebackbone 101 through one or more routers 123, 124, 125, 130, 132, 134,and 135. A router is a specialized computer for processing Internetprotocol (IP) data and forwarding IP data along respective networkpaths. In the following discussion, the term local network shall be usedto refer to all types of networks that may be included in a domain.Routing domains 103 and 105 are also referred to as autonomous systems(AS). An autonomous system is a set of nodes and routers that operateunder the same administration. The domains 103 and 105 may be operatedby the same service provider (same administration) or by differentservice providers. The networks in routing domains 103 and 105 may beresidence/subscribers' home networks, local area networks (LAN), widearea networks (WAN), metropolitan area networks (MAN), or the like.

In a point-to-point (PPP) connectivity network, various types and modelsof CPE devices such as CPE devices 124 and 125, or 130, 140, and 135 areused to terminate the point-to-point (PPP) connections. One type ofpoint-to-point connectivity communications is point-to-point overEthernet (PPPoE). With various types of broadband access, e.g. digitalsubscriber line (DSL) service, connectivity may be provided via PPPoEwithin the domains 103 and 105. It will be appreciated that the numbersof networks, routers, CPE devices, and nodes (nodes are depicted by acircle with ‘N’ inscribed within the circle) have been constrained inthe example of FIG. 1 to avoid clutter.

Broadband access service, such as digital subscriber line (DSL) service,entails the use of a CPE device to terminate the DSL (PPPoE) connectionat the residence or business location of the DSL subscriber. This isillustrated in FIG. 2, which illustrates a simplified diagram of apoint-to-point connection being established.

FIG. 2 illustrates a CPE device 225 connected through an IP network 201to an access concentrator 223. In an embodiment, the access concentrator223 is a broadband remote access server (BRAS).

Typically, the CPE device 225 terminates the asynchronous transfer mode(ATM) connection, and has point-to-point over Ethernet (PPPoE) softwareto complete a user authentication process. The CPE device 225 may be arouter or a switch, or any device that terminates a PPPoE connection.The CPE device 225 contains a module configured to transmit a PPPoEpacket including a tag to uniquely identify the CPE device 225 productmodel. Access concentrator 223 is connected to a database 226 to storethe device identifier field data obtained from the CPE device 225 duringdiscovery/authentication processes. The method utilizes the packetexchange during the conduct of a PPPoE discovery process.

PPPoE has two distinct stages, a discovery stage, and a PPP sessionstage. When a host wishes to initiate a PPPoE session, it first performsdiscovery to identify the Ethernet media access control (MAC) address ofthe peer, and establishes a PPPoE SESSION_ID. Although PPP defines apeer-to-peer relationship, discovery is a client-server relationship.That is, in the discovery process, a host (the client, or CPE device225) discovers an access concentrator 223 (the server), and variousdiscovery steps are followed to permit the host and the server to havethe information required to build their point-to-point connection overEthernet. This discovery process is illustrated in FIG. 3.

The method and system disclosed herein utilizes a tag identified inInternet Engineering Task Force (IETF) RFC 2516 (A Method forTransmitting PPP over Ethernet (PPPoE)) in an innovative way todetermine which CPE devices, such as CPE device 225, are connected to anetwork. The client (CPE 225) is capable of generating a deviceidentifier code in response to receiving a PPPoE packet communicatedover a distributed network. In the first step 302 of the discoveryprocess, the CPE device 225 broadcasts a PPPoE active discoveryinitiation (PADI) packet. This PADI packet includes a tag thatspecifically identifies a product model of the CPE device 225. The tagin a particular embodiment is a host-uniq tag, and the device identifiercode is a binary number associated with a specific product model or typeof CPE device. In a specific embodiment, the binary number is a nine bitbinary number.

The access concentrator 223, such as the broadband remote access server(BRAS), transmits a PPPoE active discovery offer (PADO) packet in step304. In step 306, the PADO packet is received by the client 225, andaccepted. In response to the PADO packet receipt, an active discoveryrequest packet (PADR) packet is generated and transmitted to the server223. The PADR packet can also include a tag that specifically identifiesa product model of the CPE device 225. In step 308, the server receivesthe PADR packet, and generates and transmits a PPPoE active discoverysession (PADS) confirmation packet. The session discovery process isconcluded, and an Ethernet communication session is then conductedbetween the client 225 and the server 223.

The host-uniq tag information may be transmitted in the PADI packet.Alternatively, the host-uniq tag information may also be transmitted inthe PADR packet. Generally it is most efficient to utilize the PADIpacket for device identification, however, the CPE device could returnthe device identifier in the tag with a PADR packet as well. Whether thetag information is contained in the PADI or PADR packets, the accessconcentrator 223 receives the PAD packet, and stores the deviceidentifier code in a database (226, FIG. 2). After collection of thedevice identifier codes in the tag, the database can be used todetermine the specific product model of a CPE device based on theinformation embedded in the tag. This information is then available tobe provided to customer service representatives to diagnose and repairuser problems, thereby decreasing the number of customer site visits andsubscriber call requests required of service technicians.

An advantage provided by the disclosed method is that it facilitatesnetwork management based upon the product model of the CPE devicesdetermined to be present in the network. For example, the use of thehost-uniq tag and the unique device identifier allows broadband serviceproviders to check on the CPE devices in use on the provider's network.This information could be used to target marketing efforts, or to enablesurveys of existing equipment to determine if the existing equipmentwill work with new technologies that a broadband service provider wouldlike to deploy. It should be noted that although the examples providedthus far have discussed primarily DSL broadband services, PPPoE is anauthentication system that is not restricted to DSL.

FIG. 4 is a block diagram of an ADSL bridge/router board 400incorporating a module 415 configured to transmit a point-to-point overEthernet (PPPoE) active discovery packet including a tag. In aparticular embodiment, the tag comprises a device identifier field thatuniquely identifies a CPE product model. It will be appreciated that,with the exception of module 415, the block diagram of FIG. 4 isprovided as a generic example of an integrated microprocessor designedto meet the needs of communications applications, and as such does notrepresent the only architecture possible for CPE devices.

CPE board 400 includes a memory control module 409 with connecting Flash411 and SDRAM 410 memory components. Other components in board 400include a universal serial bus (USB) controller 419 and a USB deviceconnector 420; an ATM segmentation and reassembly (SAR) controllermodule 414; a DSL chipset 412 and DSL connector 413; a 10/100 MbpsEthernet controller module 416, transceiver 417, and connector 418. ATMcontroller module 414 and Ethernet controller module 415 have beenintegrated into the board 400 as network interfaces.

During a PPPoE discovery process, module 415 sends a PPPoE activediscovery (PAD) packet. The PAD packet includes a tag comprising adevice identifier field that uniquely identifies a CPE product model.The device identifier field can also be generated in response toreceiving a PAD packet. The PAD packet containing the tag/deviceidentifier can be a PADI packet, or alternately, a PADR packet. In oneembodiment, the tag is a host-uniq tag, and the device identifier fieldcomprises a predefined binary number embedded in the host-uniq tag. Thispredefined binary number can be a nine-bit binary device identifiercode.

FIG. 5 illustrates a data packet 500 for use in a distributed network.The data packet 500 includes a destination address field(DESTINATION_ADDR) 502 which typically contains either a unicastEthernet destination address, or the Ethernet broadcast address(0xffffffff). For discovery packets, the field 502 value is either aunicast or a broadcast address. For PPP session traffic, the field 502value contains the peer's unicast address as determined from thediscovery stage.

A source address field (SOURCE_ADDR) 504 is also contained in datapacket 500. This field 504 contains the Ethernet media access control(MAC) address of the source device. The ETHER_TYPE field 506 is set to afirst value during the discovery stage, or to a second value during thePPP session stage. The payload field 508 contains the Ethernet payloadfor PPPoE, and is discussed in detail in FIG. 6. The checksum field 510serves to verify packet integrity.

FIG. 6 illustrates an illustrative Ethernet payload that may be usedwith PPPoE. The VERSION field 602 is four bits, and identifies theversion number of the PPPoE specifications, e.g., 0x1. The TYPE field604 is four bits, and identifies the Ethernet type for a given versionof PPPoE specifications. The CODE field 606 is eight bits, and the CODEfield value depends upon whether discovery stage or PPP stage is ineffect.

The SESSION_ID field 612 is 16 bits, and is an unsigned value in networkbyte order. For a given PPP session, the field 612 is fixed, and definesa PPP session along with the Ethernet source address (504 in FIG. 5) anddestination address (502 in FIG. 5). In the discovery stage, theSESSION_ID field 612 has a different value depending upon the type ofdiscovery packet in which field 612 is contained. The LENGTH field 610is 16 bits having a value, in network byte order, that indicates thelength of the PPPoE payload 608.

A PPPoE payload 508 contains zero or more tags. A tag is atype-length-value (TLV) construct, and an example tag is shown in FIG.7. The sample tag includes a TAG_TYPE field 702 that is a 16 bit fieldin network byte order. A list of tag types that may be present in thefield 702 includes tag types end-of-list, service-name, AC-name,host-uniq, and AC-cookie tags. The TAG_LENGTH field 704 is 16 bits, andis an unsigned number in network byte order which indicates the lengthin octets of the TAG_VALUE 706.

IETF RFC 2516 defines the host-uniq tag as follows: “This tag is used bya host to uniquely associate an access concentrator response (PADO orPADS) to a particular host request (PADI or PADR). The TAG_VALUE isbinary data of any value and length that the host chooses. It is notinterpreted by the access concentrator. The host may include a host-uniqtag in a PADI or PADR. If the access concentrator receives this tag, itmust include the tag unmodified in the associated PADO or PADSresponse.” From the foregoing IETF definition, it should be clear thatalthough the present disclosure utilizes a predefined tag, the tag isutilized in a unique way to identify CPE devices, as well as to collectCPE device information at the access concentrator or database serverattached to the access concentrator, for network management purposes.

An example of a nine bit binary CPE device identifier code embedded in ahost-uniq tag is illustrated in FIG. 8. The CPE device identifier codeuses numbers in the standard binary number system to produce anyparticular CPE device number between 0 and 512. In Example 1 of FIG. 8,an Efficient Networks 5861 Router has the binary number 000000001,making its device binary number equal to 1. In Example 2, a Netopia 3546Router has the binary number 111111111, making its device binary numberequal to 512. Using the examples of FIG. 8, when a device identifiercode transmitted to the access concentrator/database from the CPE deviceis 111111111, the determination would be that this CPE device model typeis a Netopia 3546 Router. Similarly, when the identifier code receivedis 000000001, the access concentrator would determine that the CPEdevice model type is an Efficient Networks 5861 Router.

Referring to FIG. 9, another embodiment of a host-uniq tag 900 isillustrated. The host-uniq tag 900 includes a first set of data (bits1-8) 908, a second set of data (bits 9-16) 910, and a third set of data(bits 17-24) 912. The first set of data 908 forms a first field 902 thatincludes a device firmware description. The second set of data 910includes a second field 904 that includes chipset information, and thethird set of the data 912 forms a third field 906 that includes chipsetcode or firmware information. The device firmware field 902 includes aunique identifier for a particular type of firmware for a CPE device,such as a router for a DSL modem. Similarly, the chipset field 904includes a unique identity of the chipset type used by the CPE device.The chipset code or firmware field 906 identifies the chipset code orfirmware used by the chipset of the particular CPE device identified bythe host-uniq tag 900. By identifying the particular type of equipmentfor the CPE device, technical support operators and customer supportpersonnel may receive further information regarding the particular typeof CPE devices and their equipment configurations throughout thenetwork.

Referring to FIG. 10, an illustrative system that may use the host-uniqtag 900 is shown. The system includes a broadband access server 1008, acomputer network such as the internet 1010, a customer service terminal1004, and a technical staff and operations systems 1006. The technicalstaff and operations system 1006 is coupled to a report generationmodule 1012. The operations system includes an operation station for useby operations personnel to access device information for the remote DSLCPE devices. The broadband server 1008 includes a memory 1002 thatstores the host-uniq tag 900. The host uniq-tag 900 is stored in thememory 1002 upon retrieval from remote CPE devices using thepoint-to-point over Ethernet protocol during the discovery phase. Thehost-uniq tag 900 may be retrieved and distributed to either thecustomer service terminal 1004 or the operation system 1006 via theinternet 1010.

The customer service terminal 1004 provides a display screen forcustomer help desk personnel that are assisting far end customers suchas DSL subscribers with connectivity and other service issues. Thecustomer service terminal 1004 may display to the customer supportpersonnel information regarding the remote CPE device such as aparticular device's firmware, chipset or chipset code firmware asdetermined by the host-uniq tag 900. Similarly, the technical staff andoperations system 1006 may retrieve the host-uniq tag 900 and evaluatethe tag 900 to determine CPE equipment information throughout thenetwork. The technical staff may use such information fortroubleshooting and operations personnel may use such information forproviding technical support as well as equipment updates and othertechnical deployments. For example, when the operations staff evaluatesnetwork performance and errors, the staff may characterize CPE equipmentfailures based on the particular information within the host-uniq tag,such as the particular device firmware, chipset, and chipset codes inuse. A network report of the various distributed CPE units may then beprepared and presented by the report generation module 1012. In suchmanner, operations personnel and technical staff may evaluateperformance of the CPE devices and different equipment types as well aschipsets and firmware deployed within the network to provide enhancedtechnical performance and capabilities.

Referring to FIG. 11, a method of communicating the host-uniq tag isillustrated. A PPPoE (Point-to-Point over Ethernet) active discoveryinitiation (PADI) packet including a host-uniq tag from a DSL customerpremise equipment (CPE) device is communicated to a broad-band remoteaccess server (BRAS), at 1102. A device identifier that includes afirmware identifier, a chipset identifier, and a chipset firmware codefrom the host-uniq tag is then retrieved for the particular DSL CPEidentified, at 1104. The DSL CPE device identifier is stored in a memoryeither locally or at an external database, at 1106. A PPPoE activediscovery offer (PADO) packet is then communicated to the DSL CPE, at1108. A PPPoE active discovery request (PADR) packet is communicated tothe BRAS, at 1110, and a PPPoE active discovery session confirmation(PADS) packet is communicated, at 1112. The point-to-point connection isthen established over the Ethernet between the DSL CPE and the BRAS, at1114.

Referring to FIG. 12, a method of retrieving and using the host-uniq tagthat provides a CPE device identifier is illustrated. Device identityinformation from a DSL CPE is communicated to an equipment host, at1202. The DSL CPE device identity is then retrieved at a customersupport terminal, at 1204. The DSL CPE device identity is retrieved inan operations and technical support system and reports are preparedbased on the DSL CPE device identity, at 1206. A device type of the DSLCPE is then determined within the network based on the device identity,at 1208, and surveys may be performed on the existing CPE devices withinthe network to determine suitability of such equipment with respect toupdated technology deployments, at 1210.

Thus, a system that uniquely identifies a device identity and equipmenttypes including device firmware, chipset types, and chipset codes orfirmwares for particular DSL CPE deployments may be retrieved from avariety of units deployed within a distributed network. A technicaloperations system customer service terminal may receive access to suchdevice identifying information to provide for improved service andsupport of the network.

The above disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover all suchmodifications, enhancements, and other embodiments which fall within thetrue spirit and scope of the present invention. Thus, to the maximumextent allowed by law, the scope of the present invention is to bedetermined by the broadest permissible interpretation of the followingclaims and their equivalents, and shall not be restricted or limited bythe foregoing detailed description.

1. A system comprising: a broadband access server responsive to a remotedigital subscriber line (DSL) customer premises equipment (CPE) device;and a communication path to provide for data communications with thebroadband access server; wherein the broadband access server receives adata packet that identifies a particular type of CPE device.
 2. Thesystem of claim 1, wherein the data packet includes a device identifiercorresponding to the DSL CPE device.
 3. The system of claim 2, whereinthe device identifier includes a plurality of data fields.
 4. The systemof claim 3, wherein the plurality of data fields includes a devicefirmware field, a chipset field, and a chipset code field.
 5. The systemof claim 2, wherein the broadband access server receives a plurality ofdevice identifiers associated with a plurality of different DSL CPEdevices within a network.
 6. The system of claim 1, wherein thecommunication path is a point to point over Ethernet communication path.7. The system of claim 2, wherein the broadband access server is coupledto a database and wherein the device identifier is stored in thedatabase.
 8. The system of claim 1, wherein the data packet is ahost-uniq tag portion of a point to point over Ethernet active discoverypacket.
 9. The system of claim 8, wherein the discovery packet is aninitiation packet communicated from the DSL CPE device to the broadbandaccess server during a discovery stage process.
 10. A communicationsystem comprising: a host server having access to a remote digitalsubscriber line (DSL) customer premises equipment (CPE) device, the hostserver receiving a device identifier associated with the DSL CPE device;and a customer service terminal for use in connection with acommunications network coupled to the host server, the customer serviceterminal receiving the device identifier and displaying the deviceidentifier to a user of the customer service terminal.
 11. Thecommunications system of claim 10, wherein the device identifierincludes a firmware identifier and a chipset identifier associated withthe DSL CPE device.
 12. The communications system of claim 10, furthercomprising an operations station, the operations station receiving andstoring the device identifier, the operations station coupled to areport generation element to display a report that includes the deviceidentifier.
 13. The communications system of claim 12, wherein thereport includes a plurality of device identifiers associated with aplurality of DSL CPE devices within the communications network.
 14. Thecommunications system of claim 10, wherein the host server is abroadband remote access server coupled to the customer service terminalvia an intermediate computer network.
 15. The communications system ofclaim 10, wherein the device identifier is communicated as part of ahost-uniq tag message in accordance with a discovery phase of apoint-to-point over Ethernet initiation procedure.
 16. Thecommunications system of claim 15, wherein the host-uniq tag is a 24 bitbinary number.
 17. The communications system of claim 10, wherein thedevice identifier includes a firmware identifier, a chipset identifier,and a chipset firmware identifier.
 18. A system comprising: a broadbandaccess server responsive to a remote digital subscriber line (DSL)customer premises equipment (CPE) device, the broadband access serveradapted to receive a data packet during a discovery phase that includesa device hardware identifier corresponding to the DSL CPE device. 19.The system of claim 18, wherein the device hardware identifiercomprises: a firmware identifier and a chipset identifier.
 20. Thesystem of claim 18, further comprising: a database adapted to store thedevice hardware identifier.